Communication hub for video game development systems

ABSTRACT

A video game development system for enhancing communications between development tools and video game platforms or running games. The system includes a communications hub module running on a computer or server and communicatively linked with first and second video game platforms to allow the communications hub module to forward messages to and receive messages from the game platforms. Memory accessible by the communications hub module stores communication data sets or libraries controlling communications with the game platforms. A video game development tool is provided in the system and is communicatively linked with the communications hub module. The development tool transmits messages formatted based on a client-side communications library defining communications with the hub module. The hub module receives the transmitted messages, generates game platform messages from the received messages based on the platform communication libraries, and forwards the game platform messages to the first and second video game platforms.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/328,619 filed Dec. 4, 2008 and entitled “Communication Hub for VideoGame Development Systems Having a Video Game Development Tool and VideoGame Platforms with Communication Libraries,” which is incorporatedherein by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates, in general, to video game development andcommunications between development tools and video game platforms, and,more particularly, to systems and methods for facilitating andsimplifying data transfer and communications within a video gamedevelopment system or network such as between video game developmenttools and multiple video game platforms.

2. Relevant Background

The video game market has moved from a smaller niche market to amulti-billion dollar market. The demand for new video games is growingrapidly as the size and demographics of game players continues toexpand. Also, video games used to be made for only one or two gameplatforms, but now there is a demand for video games that can be sold onnumerous platforms including standalone game consoles, computers,handheld portable gaming devices, and other electronic devices such ascellphones, digital music players, and personal digital assistants(PDAs). As a result, there is significant competition among gamedevelopers to create video games to meet the growing demand in a timelyand efficient manner and, often, for these games to be able to run asdesired on differing platforms or devices.

Large-scale, commercial video games are typically created by largedevelopment teams with the development process taking 1 to 3 years andcosting millions of dollars. A typical development team may includeproducers to oversee production, game designers, artists, programmers,level designers, sound engineers, and testers with some team membershandling more than one role. The development team works in acollaborative manner to create game content (or game assets) and gamecode, which together may be thought of as a game application, that canbe run by a gaming engine on a particular game platform to provide thegame to a player.

For example, programmers may write new source code, artists may developgame assets such as characters or scene objects, coloring schemes,textures, 3D models of game elements, and the like, sound engineers maydevelop sound effects and music, writers may create character dialog,and level designers may create advanced and eye-catching levels. Tosupport these team members, numerous game development tools, such asMicrosoft XNA, Maya from Autodesk, Inc., and the like, are now availablefor use in designing and creating game content including creating andmodeling characters and even for defining game logic (e.g., how high acharacter jumps, how much life does a Character gain or lose based on agame event, how fast does a character or game element move, and so on).However, typically a complete engine has to be purchased, which causesmost game developers to try to build their own tools. Additionally, eachvideo game console or platform developer typically will make a softwaredevelopment kit (or SDK or devkit) available to game developers, andeach SDK may include applications or tools that are useful in creatingnew video games. Each SDK may also include a communications libraryand/or interface (e.g., platform communications data) to facilitatecommunications with a game platform (e.g., the platform running a gameunder current development or running a built game for testing or use bya developer to see how a new character, asset, game parameter, or thelike is working in the game).

Currently, development tools used in the video game industry rarelycommunicate with each other and, if they do, the tools typicallycommunicate and function using a one-to-one connection. Specifically,the tool communicates with a game running on a particular video gameplatform with a connection between the tool running on a developer'sworkstation and the game platform. For example, the development tool maygenerate a platform client on the workstation to provide an interfacewith the running game, and the tool may be required to manage acommunication socket to support these communications. Each game platformtypically utilizes differing interfacing and communication protocols (orat least have some differences), and each development tool is requiredto understand how to communicate with each game platform that may beused with the tool. Presently, a game developer may be working on avideo game that needs to operate on more than one game platform, and thedevelopment for each platform often occurs along parallel paths as it isdesirable (or required) for games to be released concurrently for eachof the game platforms.

Hence, there remains a need for improved methods and systems forsupporting communications during video game development. Preferably,such methods and systems would support and simplify communicationsbetween video game development tools and differing video game platforms.

SUMMARY OF THE INVENTION

The present invention addresses the above problems by providing methodsand systems for facilitating and simplifying communications betweenvideo game development tools and video game platforms (or games runningon such platforms). A central hub communications application is providedthat abstracts the knowledge of the video game platforms as well as theexistence of other video game development tools. The video gamedevelopment tools can communicate with any game platform and with eachother without requiring specific knowledge of the intended recipientsand their communication rules or protocols. To this end, the central hubcommunications application or module has access to the data or knowledgeof how to connect and communicate with each video game platform in avideo game development system or network (e.g., has access to platformcommunication libraries (such as those provided with game platform SDKsor the like) that may be thought of as communication data sets orlibraries). In contrast, the video game development tool only has aclient-side communications library (e.g., access to such a library inmemory of the development workstation or computer or as a librarybuilt-in to the tool) that allows the tool to communicate with thecommunications hub application. The hub application receives thetool-sent messages, processes these messages as necessary based on thevideo game platform communication data sets, and forwards the messagesto the appropriate recipients/clients (e.g., video games running on oneor more platforms, to another development tool, or other interestedclient).

More particularly, a video game development tool is provided forfacilitating communications with a first video game platform and asecond video game platform (e.g., two or more platforms distributed bytwo or more companies), with the game platforms providing two differentcommunication libraries defining messaging and other communications withthe platforms or games running on such platforms. The system includes acommunications hub module running in the system such as on a hub orcommunications server, and the hub server is communicatively linked withthe first and second video game platforms to allow the communicationshub module to forward messages to and receive messages from the gameplatforms. The system also includes memory or data storage that isaccessible by the communications hub module and that stores the firstand second communication data sets (e.g., first and second or differingcode libraries that may be linked into the system). A video gamedevelopment tool is provided in the system running on a computer systemsuch as a developer workstation or other computing or electronic device.The development tool is communicatively linked with the communicationshub module, and, in this regard, the development tool transmits messagesconfigured or formatted based on a client-side communications librarythat provides information such as communication protocols forcommunicating with the communications hub module. In operation, thecommunications hub module receives the transmitted messages from thedevelopment tool, generates game platform messages from the receivedmessages based on the appropriate first and second communication datasets, and then forwards the game platform messages to at least one ofthe first and second video game platforms.

The messages from the video game development tool often will includegame data for a video game running on both the first and second videogame platforms, and, in these cases, the game platform messages areforwarded to both game platforms from the hub module. The hub module mayprocess each of the messages from the tool to determine or identify alist of recipients for each of the game platform messages it creates.The list of recipients may be based on a set of addressees provided inthe tool messages or may be based on the message content (e.g., torecipients interested in particular game data such as particular logic,game assets, game parameters/variable values, and the like). In manycases, the game development system will include additional gamedevelopment tools linked to the hub module, and these tools may receivemessages from the first or original game tool when they are identifiedin the set of addressees or when placed on the list of recipients by thecommunications hub module based on the message content (e.g., anothertool may be interested when certain game data is modified by anothertool). In this way, tool-to-tool communications are facilitated orprovided within the development system via the hub module. The list ofmessage recipients may be determined by the hub module from a list ofclients that have been registered with the hub module to receivemessages from video game tools, and the registered clients may includesubsystems of a video game running on one or both of the game platforms.The development tool may use a single communication socket to send thetransmitted message to both platforms via the hub module while the hubmodule may act to provide a communication interface with the gameplatforms in part by maintaining communication sockets or clients forthese game platforms (e.g., to implement the protocols or communicationrules/definitions provided in the first and second communication datasets).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram of a video game development systemor network configured according to prior communication methods;

FIG. 2 illustrates a functional block diagram in contrast to the systemof FIG. 1 shows a video game development system or network adaptedaccording to an embodiment of the invention with a developercommunications huh facilitating communications between game developmenttools and games running on differing video game platforms and,optionally between the tools themselves;

FIG. 3 illustrates a functional block diagram of video game developmentsystem or network providing additional detail of an exemplaryimplementation or embodiment illustrating that games use a client-sidecommunication library (that may be built into each tool) to create oruse a single communication socket to transmit and receive game data ordevelopment messages from the central hub application;

FIG. 4 illustrates a development system or network illustrating in moredetail one exemplary computer system useful for implementing thecommunication methods, authoring methods, testing methods, and otherfunctionality described herein;

FIG. 5 is flow chart illustrating generally a game development orhub-based communication method of an embodiment of the invention;

FIG. 6 is a functional block diagram of a game development system ornetwork according to an embodiment of the invention showing use of alive authoring module along with a communications hub application tofacilitate tool-to-game communications and to support live, real timeauthoring of video games;

FIG. 7 is a flow chart of a live authoring process of an embodiment ofthe invention such as may be implemented by operation of the system ofFIG. 6;

FIGS. 8A and 8B illustrate screenshots from display devices of two gameplatforms or consoles running the same video game being developed byauthoring methods described herein;

FIGS. 9A and 9B illustrates screens shots from display devices of twodifferent game platforms running similar to FIGS. 8A and 8B after liveauthoring is used to update a set of game data or assets, which showsreal time display of changes to a game by operation of one or more gametools and how such changes are implemented uniquely by two platforms;

FIG. 10 illustrates a functional block diagram of a game developmentsystem (e.g., a simplified version of the systems of FIGS. 2-4 and 6 andcomponents not shown in FIG. 10 may be included in the system of FIG.10) adapted for collaborative authoring of a video game;

FIGS. 11A and 118 illustrate video game platform screenshotsillustrating live authoring of a running game and also showauthoring/development being performed in a collaborative way with twodevelopment tools (and/or with two authors/developers operating suchtools in some examples while in others a single author may work two ormore tools in a self-collaborative manner);

FIG. 12 is a functional block diagram of a video game testing anddevelopment system (e.g., that may include at least some of thecomponents from FIGS. 2-4, 6, and 10) showing use of a communicationshub application and playtesting statistics gathering tool to facilitatetesting of a video game including obtaining real time feedback from aset of players or testers for modifications to the game data or testedportion of the video game;

FIGS. 13 and 14 illustrate screenshots of test monitoring interfacesthat may be provided by the playtesting statistics gathering tool orother devices of the system of FIG. 12 to allow a user such as a gamedeveloper to access game test data in real time or “live” and also toview aggregated and/or processed data for the group of players ortesters in a real time or live environment; and

FIG. 15 is a flow chart showing the processes of an exemplaryplaytesting method providing real time feedback to developers or testmonitors.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Briefly, embodiments of the present invention are directed to methodsand systems for managing communications within a video game developmentsystem or network. Specifically, a game development system or network isdescribed that lessens the processing overhead, usage complexity, andmaintenance requirements for each game development tool used by a gamedeveloper by providing a central hub communication application in thedevelopment system or network that establishes a communicationinterface(s) between each tool and differing game platforms. The hubcommunication application (or the server running such an application)acts as a message passing hub that extracts (or determines) therecipients for a message issued by a development tool and transmits thecontent (e.g., game data such as modified game logic to be used by agame engine on a platform, a game asset such as a new character orobject in 3D model or other form, and/or a game parameter such aslighting level, texturing, and the like) as-is or with reformatting tothe recipients in the game development system or network.

As background, the following description provides examples of particularcomputers, computing devices, workstations, video gameplatforms/consoles, communication networking and digital connections,memory devices, and other computing hardware and software resources usedin video game development. However, it will be understood that these areonly representative examples of useful implementations of the inventionand not as limitations to its breadth. Further, embodiments of theinvention may be thought of generally as a computer-based method forsupporting communications, authoring, and testing during gamedevelopment (e.g., while operating a developer terminal, node, PC,workstation, or the like and using one or more video game developmenttool), the particular software, firmware, and/or hardware used toimplement the described methods and functions are also not limiting ofthe invention. In general, the algorithms, routines, and processesdescribed herein may be implemented upon nearly any computer-readablemedium that can cause a computer or computer system to perform acorresponding function. For example, the hub communication applicationmay be provided as software or programming code for causing a computingdevice such as a developer's computing device or a central/networkedserver to perform particular functions as part of creating a gamedevelopment computing and communication environment and may be stored ona memory device of nearly any node accessible via wired or wirelessconnections by video game development tools and run on a device thatuses one or more processors or CPUs to run the software. The video gamedevelopment workstations likely will include a number of input/outputdevices (I/O devices) such as a keyboard, a mouse or trackball or thelike, a touchscreen or pad, a voice recognition mechanism, and the like.A monitor or monitors will also be provided to allow the user to viewone or more user interface (such as windows created as part of thecomputing environment to view and/or access video game tool interfacesand view/modify game data such as game logic, game settings, gameassets, game parameters, and the like). Such user interfaces may benearly any combination of menus, screen designs, keyboard commands,command language, and the like (including in some cases mice, touchscreens, and other input hardware such as voice recognition) to allow auser to interact with a computer and with video game digital assets anddata stored in memory in a particular computing environment. Theinvention may also be implemented using one or more data servers thatmay communicate with the workstations over a digital communicationsnetwork such as the Internet, a local area network, a wide area network,or the like using any of a number of well-known or later developedcommunications protocols (wired or wireless), and the browsers andrelated applications may be provided as web applications accessible inparticular computing environments.

To assist in understanding some of the benefits of such a hub-basedcommunication system and method as part of the game development andtesting process, it may be useful to discuss an existing or moreconventional game development system 100 as shown in FIG. 1. In aconventional game development system 100, a number of developers may useworkstations 110, 128 to present a computing or working environment 112,130 in which one or more development tools 114, 134 (such as the MayaPlugin, a Variable Tweaker tool, a logic update tool, and the like) arerun so as to develop a video game. This game may be run on a number ofdiffering video game platforms or consoles as shown as platform A andplatform B with the running games shown as boxes 160, 170. The computingenvironment 112, 130 of each workstation 110, 128, may include memory ordata storage 117, 137 that is used to store a communication/interfacelibrary or platform communications data 119, 139. Such communicationsdata may define all or some subset of the messaging formats andtransmittal protocols expected by each video game platform, and,typically, each of the sets of platform communications data 119, 139defines an at least partially different set of rules that must befollowed for the tools 114, 134 to communicate properly with the runninggames 160, 170 on the platforms. If a developer were working with justone platform, this may not be too much of an issue, but more often eachdevelopment workstation 110, 128 and running tools 114, 134 are used todevelop a game 160, 170 for use on two, three, or more video gameplatforms. Hence, it is important for the tools 114, 134 to be able tocommunicate with each platform or game running 160, 170 on such varyingplatforms (such as those developed and distributed by Sony, Microsoft,Nintendo, and other gaming platform manufacturers).

Presently, development tools 114, 134 used in the video game industrytypically provide no communications or, if they do provide a form ofcommunication, function as shown by using a one-to-one connection 120,126, 140, 146 between the tool 114, 134 and the running games/platforms160, 170. To establish communications, the tools 114, 134 may be thoughtof as creating communication clients 116, 122, 136, 142 for each game160, 170 that they wish to communicate with during development/operationof system 100. Further, such one-to-one communications may be thought ofas requiring the tools 114, 134 to each create and manage communicationsockets 118, 124, 138, 144 to allow direct messaging 120, 126, 140, 146to and from the running games 160, 170. In the system 100, each toolneeds to understand how to communicate with each platform 160, 170separately. For example, a communication link along with messagesformatted as required by the communication data 119 for a particularplatform 160 likely cannot be used for sending a message with the samecontent to the other platform 170. In a more concrete example, a certaintool 114 or 134 may use one set of communication data 119, 139 (e.g.,information/data provided in a video game platform in developer's SDK orthe like) to update objects or other game assets/data on a Sony PS3platform (or first platform) but could not use these same communicationtechniques/methods to send messages updating the same objects or othergame assets/data on a Microsoft Xbox 360 (or second platform). Further,the one-to-one communication technique has not been useful in allowingtools to communicate between each other or with other tools as the tools114, 134 generally would need to have explicit knowledge of the otherrunning tools in order to establish a connection.

In contrast, FIG. 2 illustrates a game development system or network 200that is adapted such that the individual games do not have to haveknowledge of the particular platform communications data and/or rules oreven what games and/or tools are “listening” or connected to the gamenetwork 200. The system 200 again includes a pair of developerworkstations 210, 250 that are running video game development tools 212,251, but only a single connection 214, 252 is maintained/used by eachtool 212, 251 to communicate with both games 230, 240 running on twodiffering platforms and, optionally, with other tools (which is nottypically done within the system 100 of FIG. 1).

The system 200 simplifies game development communications by including adeveloper communications hub 220 (e.g., a server or other computingdevice that may take the “server” role for messaging within system 200).The hub 220 runs a central hub communications or message-passingapplication that abstracts the knowledge of platforms and existence ofother tools from the individual tools 212, 251, and such acentralization and abstraction of communications duties allows the tools212, 251 to communicate with each other and with any game platform 230,240 without requiring specific knowledge of the intended recipient andpotential interfacing, message formatting, and other communicationrequirements imposed by that recipient. The system 200 does thisgenerally by centralizing the knowledge of how to connect with differentplatforms 230, 240 into a central hub application and, in some cases, bybuilding a client side communications library into each tool (not shownbut used to allow the tools 212, 251 to communicate with the hubapplication with a relatively simple messaging protocol that can be usedfor all of its messaging and data transfer in system 200). Such alibrary may also be used to allow the platforms 230, 240 to connect withthe hub 220 (or hub communication application running thereon).

As shown, the hub 220 provides an interface to a client 222 for tools212, 251 to communicate with games running on a first platform 230(shown as Platform A) as well as communication clients 224, 226 fortools 212, 251 to communicate with games running on a second platform240 (shown as Platform B in FIG. 2). The hub 220 includes memory or datastorage 225 for storing communications data or libraries 227 (such asthose provided in video game SDKs and the like) for each of theplatforms 230, 240. The information is used by the hub applicationrunning on hub 220 to provide the interfaces between the tools 212, 251that send the hub-formatted messages over links 214, 252 and games 230,240 running on differing platforms and linked to hub 220 via links 228,242. The communications may be managed, in part, by the hub applicationcreating communications clients 222, 224, 226 based on the platformcommunications data 227 in memory 225. During operation of system 200, atool 212 or 251 transmits a message over link 214 or 252 (such as amessage to modify a lighting setting or a texturing of an object of thegame or so on) that is formatted per the client-side hub library (notshown in FIG. 2). The hub 220 acts to determine which recipients shouldreceive the message content such as one or both of the games on the twoplatforms 230, 240 and tool 212 or 251. The hub 220 then uses theappropriate communications data/libraries 227 to reformat/translate themessage for each recipient (and/or uses the created clients 222, 224,226 to manage such communications and comply with communication rules).The hub 220 then forwards the message to the interested or determinedset of recipients in the system 200. As can be seen from the relativelygeneral illustration of system 200, the tools 212, 251 and games 230,240 need only know how to talk or communicate with the hub 220, andthere is no need for specific knowledge of the communication rules ofthe intended recipient(s) to send game information or data out onto thenetwork or system 200 and to the recipient(s). In contrast to the system100 of FIG. 1, the tools 212, 251 do not need to manage communicationclients and/or sockets for each possible platform or store/accesscommunications data/libraries for each game platform. Further, thesystem 200 allows the tools 212, 251 to communicate with each other (asis explained in more detail below).

FIG. 3 illustrates in more detail a video game development system 300that may be used to implement the communication methods of an embodimentof the invention. In this embodiment, a developer computing system 310is shown that includes a CPU 312 running two or more video gamedevelopment tools 316, 318 such as those used to create 3D models, toset or adjust game logic, to create objects, characters, or other gameassets, and so on. I/O devices 314 may be provided to allow a developerto interact with the tools 316, 318 and game data, and one or moremonitors 320 are included to view tool GUIs 322 and otherwiseview/interact with tools 316, 318 and game data. The system 310 furtherincludes memory 324 that stores client-side hub communicationsdata/library 338, and this includes data to enable the tools 316, 318 tocommunicate with the communication hub application 354 (and through thisapplication 354 with games under development 372, 382 or other ones ofthe tools 316, 318 (or tools on other systems 310 not shown). The memory324 is also shown to include a game application 330 such as a game beingdeveloped or a recent build of such a game (or this data may be storedon another memory device accessible by system 310 and other developersystems). The game application 330 includes game data such as gameassets 332, game logic 334, and game settings 336, and the gameapplication 330 can be thought of as being defined by this game data;hence, game development includes using the tools 316, 318 to create andmodify the game data in memory 324 and/or on a running game 372, 382 ona number of video game platforms/consoles 370, 380.

The system 300 also a communications network 340 that is used to connectthe developer system 310 with a hub server 350. The hub server 350includes a CPU 352 that runs a communications hub application 354. TheCPU 352 also manages memory 356 that is shown to store a list of clients358 (e.g., platforms, tools, games or subsystems of games registeredwith the hub application, and the like) for receiving systemcommunications. The memory 356 also stores platform communication data360 (e.g., SDK communication libraries for each platform 370, 380) foreach platform 370, 380 in the system 300 or expected to be added to/usedwithin system 300. The hub server 350 runs the communication hubapplication 354, and the application 354 may function to provide acommunication interface 362 between the tools 316, 318 and the gameplatforms 370, 380 (and between tools 316, 318 themselves). To this end,a communication client 364, 366, 368 may be created by the hubapplication 354 using the platform communication data sets 360 for eachplatform 370, 380 as well as rules/protocols for communicating with theworkstation/system 310.

During operation of the system 300, each of the game development tools316, 318 may use the client-side hub library 338 as a built-in orruntime communication mechanism to create and manage a hub communicationsocket or link 342, 344 via network 340 to send messages to and from thehub application 354 on server 350. These messages may include game datasuch as modifying game logic 334 or an asset 332 on games 372, 382(e.g., the same game running on two differing platforms). The hubapplication 354 processes these messages via interface 362 and clients364, 366, 368 and/or communication data 360 to determine the recipientsfor the message, to place the message in the expected format for thoserecipients, and to transmit the message over links 376, 386, 342, 344 asappropriate. The list of clients 358 may include the video games 372,382 or one of the tools 318 and each message may be sent to one, a setof or all of such recipients depending on the content (who is registeredas being interested in that type of content/message) and/or on arecipient list/addressee in the message from the tool 316, 318 (such asto a particular game or game subsystem or to any tools interested in aparticular game data).

FIG. 4 generally illustrates a game development system or network 400that may be used to implement the hub or centralize communicationtechniques and other functions/processes described herein. The network400 includes a computer system 402, which typically is used by a gamedeveloper (or member of a video game development team) and includes aprocessing unit or CPU 203 and system memory 205 with one or more gamedevelopment tools that may be run by CPU 203. As discussed above, eachof the game development tools or programs may have a built-inclient-side communications library that provides the informationrequired for the program to communicate with a central communication hubapplication running on a remote computer 250 (or on one of the developercomputer systems 402 in a distributed system/network), and, in thismanner, messages generated by the game development programs can berelatively simple and/or generic in form and be delivered via thecentral communication hub application to games running on first andsecond (or more) platforms 451, 453 that may have differingcommunication requirements (e.g., differing messageconfiguration/content, differing transmission protocols, differingcommunication and/or client interfaces, and the like such as may bespecified by each platform developer's SDK or a communication library inthe SDK or otherwise specified).

A system bus 407 couples various system components including systemmemory 405 to processing unit 403. System bus 407 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. System memory 405 includes read only memory (ROM) andrandom access memory (RAM). A basic input/output system (BIOS) 456,containing the basic routines that help to transfer information betweenelements within computer system 402, such as during start-up, is storedin ROM 456. Computer system 402 further includes various drives andassociated computer-readable media. A hard disk drive 409 reads from andwrites to a (typically fixed) magnetic hard disk 411; a magnetic diskdrive 413 reads from and writes to a removable “floppy” or othermagnetic disk 415; and an optical disk drive 417 reads from and, in someconfigurations, writes to a removable optical disk 419 such as a CD ROMor other optical media, and, of course, other removable memory devicesmay be inserted into and accessed (read and/or writing of data) via aport such as a USB or other communication port in a housing of thesystem 402. Hard disk drive 409, magnetic disk drive 413, and opticaldisk drive 417 are connected to system bus 407 by a hard disk driveinterface 421, a magnetic disk drive interface 423, and an optical driveinterface 425, respectively. The drives and their associatedcomputer-readable media provide nonvolatile storage of computer-readableinstructions, programs, procedures, routines, data structures, programmodules, and other data for computer system 402 (such as initialinstallation of the client-side communications library and/or for backupstorage/transfer of game application or game assets). In otherconfigurations, other types of computer-readable media that can storedata that is accessible by a computer (e.g., magnetic cassettes, flashmemory cards, digital video disks, random access memories (RAMs), readonly memories (ROMs) and the like) may also be used.

A number of program modules such as game development tools, testingroutines, and the like may be stored on hard disk 411, removablemagnetic disk 415, optical disk 419 and/or ROM and/or RAM of systemmemory 405. Such program modules may include an operating systemproviding graphics and sound APIs, one or more application programs,other program modules, and program data such as game data. A user mayenter commands and information into computer system 402 through inputdevices such as a keyboard 427 and a pointing device or mouse 429. Otherinput devices may include a microphone, a joystick, a game controller,wireless communication devices, a scanner, or the like. These and otherinput devices are often connected to processing unit 403 through aserial port interface 431 that is coupled to system bus 407, but may beconnected by other interfaces, such as a parallel port interface or auniversal serial bus (USB) or by wireless connections. A monitor(s) 433or other type of display device is also connected to system bus 407 viaan interface, such as a video adapter 435 such as for viewing gamedevelopment and game testing GUIs or other game data.

Computer system 402 may also include a modem 454 or other means forestablishing communications over wide area network 452, such as theInternet. Modem 454, which may be internal or external, is connected tosystem bus 407 via serial port interface 431 (or some other interface).A network interface 456 may also be provided for allowing computersystem 402 to communicate (e.g., establish communication sockets and thelike) with a remote computing device or server 450 via a local areanetwork 458 (or such communication may be via wide area network 452 orother communications path such as dial-up or other communicationsmeans). Computer system 402 typically includes other peripheral outputdevices, such as printers and other standard devices (not shown).Computer system 402 is preferably equipped with an operating systemsupporting Internet communication protocols and/or other digitalcommunications network protocols and communication interfaces (e.g., tosupport digital communications with the central communications hub oncomputer 250 via messages generated and transmitted based on thedefinitions/requirements of the client-side communication librarytypically built into the game development programs). Other types ofcomputer systems other than or in addition to the one shown are usableto practice the invention (e.g., a local area network of computers, aninteractive television, a personal digital assistant, an interactivewireless communications device, electronic devices with adequatecomputing capabilities and memory, or the like).

FIG. 5 illustrates a video game development communications method 500,as may be implemented by the systems 200, 300, 400 of FIGS. 2-4. At 504,the method 500 starts by loading or providing a central hub applicationwithin a video game development system or network. The communicationsdata or libraries for each game platform or console that is being usedor may later be connected to the network may be made available to thecentral hub application. At 510, the method 500 continues with providingclient-side communications data or a hub library to each of thedevelopment tools (or to the workstations that run such tools). Theclient side library may be a runtime library stored in the workstationmemory. The client-side libraries include the data or information (suchas messaging configuration/format and/or other communications protocols)to allow the tools to communicate with central hub application. At 520,the method 500 continues with registering development tools and/or videogame(s) with the hub application to create a recipient list for thedevelopment network or system. Tools may register to be informed whenparticular game data is altered while the video games typically areregistered in a subsystem manner to receiving communications/messagesfrom tools including modified game data (e.g., a materials subsystem, anobjects subsystem(s), a texturing subsystem, a lighting subsystem, andso on may each register with the hub application for a particular videogame running upon a game platform linked to the development system ornetwork). This aspect of the system allows tools to direct messages to aparticular subsystem instead of relying on the game to determine theappropriate subsystem itself.

The method 500 then may include the hub application monitoring thecommunication network for a next message to be transmitted from a toolor game. When a message is received at the hub, the method 500 continuesat 540 with the hub application acting to identify message recipients540. For example, in some embodiments, the tools may transmit messagesin a generic manner with no addressees specified, and in such cases themessage may be sent to all recipients on the hub recipient list or asubset interested in a particular type of message or message content. Inother cases, the message may be transmitted by the tool in a form thatspecifies one or more (a set) of recipients for the message, e.g., amessage to a game running on one platform or another tool. At 550, thehub application translates and/or reformats the message as appropriatebased on the identified recipients and the communications data (rules,libraries, and the like) associated with each of these identifiedrecipients. For example, a hub-formatted message from a tool may bereformatted or translated to comply with communications data/rules for afirst game platform and also for a second game platform. Then at 560,the method 500 continues with the hub application forwarding the messageto all identified recipients or to clients requesting the gameinformation in the message. In some cases, the hub application handlesopening communication links or sockets for each platform (and/or foreach recipient or the like). The method 500 may continue at 530 withwaiting for additional game development or related messages or end at590. Generally, the method 500 may be used for one-to-one communicationsas a tool or other sender of the development network may specify therecipient or addressee, but the method 500 also supports a one-to-manyconnection or broadcasting communication methods as a tool can make achange to a particular game data (such as tweak a portion of the gamelogic) and transmit a generic hub-format message that will be sent bythe hub application to all interested recipients (e.g., to all games orgame subsystems affected by the change). As a result, a developer doesnot have to create and send a message for each platform to have thechange implemented by running games.

FIG. 6 illustrates a game development system 600 adapted particularlyfor supporting live authoring of video games on two or more differentgame platforms or consoles (e.g., Microsoft's Xbox, Sony's Playstationconsoles, Nintendo's Gamecube or Wii, and the like). The system 600includes a number of components similar to those discussed in detailwith the system 300 of FIG. 3 with like numbers being used fbr thosecomponents and the description of FIG. 3 is applicable to FIG. 6. Forexample, the system 600 includes a hub server 350 running acommunications hub application 354 that functions to receive messages690, 691 from game development tools 316, 318 running on computer 610.These messages 690, 691 are formatted according to a hub communicationlibrary 615, 617 shown as a built-in library for tools 316, 318, and thehub application 354 acts to process the messages to determine a setrecipients specified in the message or, more typically, from content ofthe messages 690, 691 and from comparison to a client list 358 ofinterested listening clients (e.g., other tools 316, 318, games 674,684, or storage management components for the centrally located/storedgame data 644). The received messages 690, 691 are thenreformatted/translated for each recipient based on communications data360 for that recipient (e.g., what format does platform 670expect/require? and so on) and forwarded to those recipients via thenetwork 340 (or via a direct connection (not shown)).

Likewise, the developer computer system 610 is similar to system 310 inthat it includes a CPU 312, I/O devices 314, and a monitor 320 fordisplaying information including game data in tool GUIs 322. The system610 also uses the CPU 312 to run one or more game development tools 316.In this case, each tool 316, 318 is able to link to and communicate withthe communications hub application 354 using a built-in, client sidelibrary 615, 617 that defines how to interface and communicate with thehub application 354 including how to format authoring messages 690, 691.In the system 600, a data storage server 640 is included that isaccessible by the tools 316, 318 via network 340 and includes memory 642storing the game application data 644 (e.g., game assets such as createdobjects, character models and animation, game logic, parameter/variablesettings, and other information used by a game engine in running a videogame). As game tools 316, 318 access the data 644 (e.g., display currentvalues in a tool GUI or the like), a tool cache or memory 624 may beused by CPU 312 to store game data 630 such as game assets 632, gamelogic 634, and variable/parameter settings 636 for efficient access bytools 316, 318.

During operation of the developer computer system 610, a developer maycall up or use a number of game development tools 316, 318. For example,a logic adjustment tool 316 or 318 may be used that provides a GUI 322that presents the present game logic 634 or settings 636 and allows itto be readily adjusted or tweaked (e.g., how fast a character runs, howmuch high a character jumps, how many times an opponent has to be struckto fall, and so on) such as with pull down boxes with logic valuechoices, slide bars to adjust values, data entry boxes, and the like.Another tool 316, 318 may be used to create a new animation or to modifyan existing model or object such as by changing its texture, by movingits position within a screen, modifying its size, and so on via a GUI322 displayed on monitor 320.

According to one important aspect of the system 600, the developer isable to obtain instantaneous or real time feedback on these changes inpreviously built and running video games on two or more differing gameplatforms (e.g., on Sony's PS3 concurrently with Nintendo's Wii consolesand so on). As shown, the system 600 includes at least two gameplatforms 670, 680 that include game engines 672, 682 to run gameapplications 674, 684. The running video games 674, 684 functionality iscontrolled in part by the game assets 676, 686 such as 3D models ofcharacters and other animations, level design, game play logic, lightingsettings, textures, coloring, and so on. When the video game 674, 684 isrun by the engines 672, 682 a video display 678, 688 of the platform orgame system 670, 680 is used to display the game to players such astesters and, in this case, to the developers.

To provide real time feedback, the developer computer system 610includes live authoring modules 616, 618 associated with or built in toeach development tool 316, 318. The live authoring module 616, 618functions (as is discussed with reference to FIG. 7) to cause (orfacilitate) changes or additions to the game data 630 for a video gameto be broadcast as shown with authoring messages 690, 691 from the tools316, 318 through the hub application 354 to a list of recipients orinterested clients 358 of the hub server 350. The authoring messages690, 691 are formatted according to client-side hub communicationslibraries 615, 617 for receipt by the hub application 354 while the hubapplication 354 uses platform/client communications data 360 totranslate each of the messages it sends out over network 340 (ordirectly) to a list of recipients. The recipients for the reformatted(when necessary) authoring messages 690, 691 may be running gameapplications 674, 684 and other ones of the game development tools 316,318. This allows a developer to implement a change in the game assetssuch as to make a change to a character skin or clothing with one tool316 (such as Adobe Photoshop) and have that change broadcast viaauthoring message 690 for distribution in proper platform/recipient formby communications hub application 354, and the developer or use ofsystem 610 will see the results of the change in both running games 674,684 as the game assets 676, 686 are updated based on received game dataupdate messages 694, 696 transmitted by the hub application 354.Additionally, the change may be broadcast to the other game developmenttool 318 (such as Autodesk Maya) with another update message (not shown)from hub application 354. A game data update message 692 may also besent from the hub application 354 to a data or central storage server640 to cause the game data for the new game 644 to be updated to reflectthe changes made with tool 316.

In this manner, a single authoring message 690 or 691 from a tool 316,318 may be used to cause multiple changes to be concurrently implementedwithin any number of game platforms 670, 680 as well as other tools 316,318, and this can be achieved without the developer having to haveknowledge of each platform 670, 680, without creating and sendingmultiple messages, and without having to reprocess or create new buildsof the running game applications 674, 684 as the authoring is “live” orperformed with real time feedback. Rebuilds of games, in contrast, areundesirable as they may take several minutes to complete.

FIG. 7 illustrates a live video game authoring method 700 of anembodiment of the invention such as may be implemented by operation ofthe system 600 of FIG. 6. The method 700 starts at 706 such as bychoosing a number of video game development tools for use in creating anew video game, loading such tools onto a workstation (or making thetools available from a server in a network or distributed computingenvironment). The video game may be designed for use on more than onevideo game platform, and at 705 this set of video game platforms orconsoles will be selected or defined. As discussed above, modificationsto game logic, objects, textures, lighting, coloring, and other gameassets/data may be processed by a game engine of each platformdifferently such that it is desirable for a developer to be able to viewthe results of changes to a running game in real time on the variousplatforms (e.g., with the displays of the platforms positionedside-by-side or nearby to allow ready comparisons of displayed games).

At 710, the method 700 continues with configuring the game developmentsystem for hub communications, e.g., for allowing a tool to send asingle message in a format understood by the hub application that canthen determine a recipient list, translate/reformat the message based onthe communication requirements of each recipient, and broadcast/forwardthe authoring or game data update message to the set of recipients. Tothis end, client-side libraries may be provided on the game developer'scomputer or workstation such as modules built in or accessed by eachgame tool to allow the tools to communicate with properly formattedmessages to the huh application, and hub application is provided in thesystem and communicatively linked to the tools (such as via acommunication network). The hub application is provided access tocommunications libraries or data sets (e.g., communications librariesprovided with a game platform SDK and the like to manage communicationswith clients associated with a potential recipient list within thedeveloper system, which may include other development tools (e.g., a PCclient may be utilized/supported by the hub application) as well as gamedata central storage.

At 720, the method 700 continues with providing and/or loading a liveauthoring module or modules on the developer computer system(s). Forexample, a single authoring module may be provided to support a set ofdevelopment tools or an instance may be provided for each developmenttool to support communications with the hub application upon changes tothe game data with a tool. At 728, the method 700 continues with adeveloper using the game development tools (or other mechanisms) tocreate new game assets or to modify existing game data or assets (suchas changing the logic to make a particular move or portion of a gameeasier or harder).

At 730, the method 700 includes determining whether automated messaginghas been activated within the live authoring module. For example, it maybe a default setting for the live authoring module for authoringmessages to be broadcast automatically upon a game development toollinked to an authoring module being used to create or update a gameasset or game data. In other embodiments, the game developer may begiven the option of making such messaging automatic or to select anoption in which they are prompted by the authoring module after making achange with a tool to send an authoring message to the running videogames (and other interested clients/recipients) via the centralcommunication hub. In this regard, if the messaging is not automated(e.g., handled by the authoring module without further action by thedeveloper), the method 700 continues at 740 with the live authoring toolprompting the user or developer to transmit a game update message suchas by displaying a message in workstation monitor or tool GUI asking ifthe updated data should be sent in an authoring message or whether toremind the developer later (e.g., upon another asset addition ormodification). At 746, the method 700 includes determining whether themessage transmittal is authorized. If not, the method 700 may continueat 740 as shown or return to step 728 (e.g., await a next change to agame asset). In other embodiments/implementations, the data is alwayssent if possible and typically always handled. In such cases, the method700 is adapted to from prompting a user, especially when they may end upskipping one change and then allowing a second change, which isdependent upon the first, which may cause problems.

If messaging is automated or has been authorized, the method 700continues at 750 with the live authoring module acting to transmit theauthoring message to the communications hub application. The authoringmessage is in a format called for by the hub application (e.g., in aclient-side library), and the message content typically is the game dataaddition (e.g., a new object or character) or a change to an existinggame asset such as to modify game logic, change a variable or parametersetting or position, and so on. At 760, the hub application receives themessage, determines a set of recipients or clients to receive themessage, translates each based on a corresponding communications dataset defining/controlling communications with that recipient, andtransmits or forwards the messages with game data to each identifiedrecipient.

At 770, the game data for the video game may be updated to reflect thegame data in the authoring message (e.g., in centralized storagelocation accessible by one or more developers working on one or moreworkstations). At 780, the method 700 continues with the game enginerunning the game application with the updated game data or assets aspresented in the authoring message broadcast from the development tool.The method 700 may end at 790 or return to step 728 to allow thedeveloper(s) to make additional revisions or additions of the game data.In this manner, the developer can author a change or set of changes to avideo game, broadcast a single authoring message with one, two, three,or more additions and/or changes to the game data or assets, and viewthe resulting effects these changes/additions have on the running gameapplication within one, two, or more game platforms or consoles.

FIGS. 8A and 8B illustrate screen shots 810, 820 of a video game thatmay be running upon two differing game platforms such as by twodiffering companies' game consoles. Often, it is preferable to create asingle set of game data for a video game rather than creating a separateset for each game platform, and while a game application running on twodiffering platforms may appear nearly identical when displayed on theconsoles' monitors there typically are at least minor differences in thedisplay. In some cases, a change to a game asset such as a lightinglevel or texture of a scene element may have a desirable appearance onone platform while having an appearance or resulting effect that isundesirable on a second platform. Additionally, different pre-processingsteps may be employed that take source data to engine ready. These stepscan be run as part of the send to the hub or, in some cases, by anothertool listening for updates going through the hub that would intercept,process, and re-send data.

For example, the game data or assets used by a game application and/orgame engine running the game application may be identical for the screenshots 810, 820. As shown, a game character 812 with clothing 814 isshown to be jumping from the floor/ground 818 toward the top of a gameobject (e.g., a column in this case) 816. The character 812 is shown tojump to a particular height, H_(jump), while the object 816 has aparticular height, H_(object). In screen shot 820 corresponding to adifferent game platform, the character 822 is shown to have clothes 824,and the clothes 824 may have a different appearance than clothes 814.Similarly, the game shot 820 shows the floor 828 with a texture similarto that of floor 818 but with some small differences. Yet further, anobject 826 is included but its height, H_(object), differs from that ofobject 816 and/or the height of the jump, H_(jump), may differ for thecharacter 822. From this illustration, it can be seen that a set of gamedata may be processed differently or produce differing results for agame application run on two differing platforms. This makes it desirablefor a developer to view a running game while (e.g., “live”) they makechanges to the game data or assets and, preferably, to view the samegame running on two or more platforms to allow a determination ofwhether the change or addition to the game assets is desirable oreffective.

FIGS. 9A and 9B show screen shots 910, 920 of the video game at the samelocation/position in the game and for the same two platforms but afterseveral changes have been made to the game data. The change may beimplemented with live authoring techniques described herein such as bychanging several game assets and then issuing a live authoring messageswith the changed content. In some embodiments, a single change oraddition may be made with each message while other embodiments may havea developer performing several changes and sending all changes within asingle authoring message. In the illustrated example, a developer hasused game development tools to make several changes to the game data.The game logic has been modified such that the height of the jump,H_(jump), of the character 912, 922 in response to a player input isgreater. The object 916, 926 has also been modified by reducing itsheight, H_(object). Further, the texture of the flooring/ground 918, 928has been modified.

The modified game assets/data is used by the two game engines/platformsassociated with screen shots 910, 920 but, as is shown, the changes tothe game data results in at least partially differing results or effectsfor the game display or game output. For example, the texturing of thefloor 918, 928 may appear somewhat different, the height the characterjumps may be slightly different, and/or the height of the object 916,926 may differ for the two platforms with the same game data. Of course,not every game data change or addition will result in a different gameeffect for differing platforms, but it is very useful for a developer tobe able to verify the effects of their editing or authoring in real time(or nearly instantaneously as the game display is modified based onchanges) and for the effects to be verified/tested for all platforms forwhich the game is being designed. The live authoring tool with use ofthe communications hub application technology allows live authoring tobe carried out in a game development system with efficient messaging andwithout requiring iterative steps of creating new builds of a game onevery platform (e.g., a useful portion of the live authoring processesis that builds of multiple games running on differing platforms receivegame data changes concurrently with the tool or developer workstationsending message(s) to the communications hub). Also, as discussed,multiple content/logic changes can be sent/made in real time, whichsignificantly increases the efficiency of a developer making numerousedits/changes to a video game.

In some game development environments, it is desirable for two or moregame development tools to communicate with the same live instance of avideo game on one or more video game platforms. For example, it may beuseful for a developer to use two tools concurrently to work on a videogame including changing differing portions of the game data (e.g., leveldesign and game assets such as texturing, lighting settings, game logic,and so on). In other examples, two game developers may wish to work onthe same portion or location within a video game concurrently with thesame or differing game development tools. In some embodiments, a gamedevelopment system configured as discussed above (e.g., see FIGS. 2-4and 6 and the like) with a hub application may be used to allow content(or game data) changes performed or made by separate individuals (e.g.,development team members) to be reflected in the same gamesimultaneously (or at least without requiring the game instance to bestopped, one set of changes made, rebuild the game, and then allow anext developer to work on the game). In some cases, the developers'respective tools may listen to communications (e.g., register as clientswith the hub or the like) and update their game data on the client end(e.g., on the separate workstations) in real time or on an ongoing/livemanner. As a more specific example, a texture artist using AdobePhotoshop (or another game development tool) may be workingsimultaneously or at least partially concurrently with a world designerusing Autodesk Maya (or another game development tool), and as thetexture artist tweaks or updates the texture, the change may bereflected in a running game instance on a set of video game platformsand also in the world designer's view or tool GUI of Maya. Additionally,the world designer may be changing or tweaking game data such as objectpositions and the changes they are making may reference the same texturebeing adjusted or authored by the other developer. Such collaborativeauthoring with real or near real time feedback on a running gameinstance and game tool GUI had previously been unavailable in theone-to-one (tool to game) connections used by game developers.

FIG. 10 illustrates a video game development system 1000 adapted forsupporting collaborative authoring methods and functions. Note, thesystem 1000 is shown in a somewhat simplified manner to highlightportions that may be used in collaborative authoring but the system 1000may include any of the components and software devices discussed hereinsuch as shown in FIGS. 2-4 and 6. To support collaborative authoring ofa video game, the system 1000 includes a set of developer systems 1010,1030 that may be operated by the same or, more typically, differentauthors or game developers. A monitor 1012, 1032 is provided on eachsystem 1010, 1030 along with one or more game development tools 1020,1040. The game development tools 1020, 1040 are communicatively linkedwith a hub 350, which runs a communications hub application 354 asdescribed throughout this description, and the hub application 354 usesplatform and other client communication libraries or rule sets 360 andregistered client lists 358 to support communications between the tools1020, 1040 and a live, running video game instance 1074 as well as withother tools 1020, 1040 on the same or differing computers.

During operation of the system 1000, the game development tools 1020,1040 access centralized game data storage (not shown in FIG. 10) andstore game data 1028, 1046 in memory or cache 1026, 1044. The tools1020, 1024 use the monitors 1012, 1032 to display a tool GUI (or toolinterface) 1014, 1034 that includes or is created based upon game data1028, 1046. Concurrent with operation of the tools 1020, 1040, thesystem 1000 includes one or more game platforms 1070 that use a gameengine 1072 to run an instance 1074 of the video game being worked on bythe tools 1020, 1040, with the instance 1074 being run based on thepresent game data 1076 including any updates or changes 1078 generatedby use of the tools 1020, 1040. The game engine 1072 may use or supportuse of one or more display and/or output devices 1080 to provide thegame output 1084 (e.g., video images, sounds, music, dialog, and/orother audio output, controller tactile feedback, and the like defined orprovided by the running game instance 1074).

In this exemplary embodiment 1000, a hub communications library or dataset 1024, 1042 is provided for each tool 1020, 1040 and is used by thetools 1020, 1040 to transmit or broadcast authoring messages 1050, 1052to the hum 350. The communications hub application 354 then determinesrecipients, translates the messages 1050, 1052 (which are in a formatexpected/required by the hub application 354) to a formexpected/required by each identified recipient, and then transmits a setof game data update messages 1054, 1056, 1058. In the collaborative modeof operation, the client list 358 may include the tools 1020, 1040(e.g., each tool 1020, 1040 listens for changes to the game data 1028,1046 it uses/references). The authoring messages 1050, 1052 aretransmitted generally after the tools 1020, 1040 are used to createupdates 1029, 1048 to the game data 1028, 1046. These changes/contentare included by the hub application 354 in the data update messages1054, 1056, 1058 such that the game data 1076 used by the live, runningvideo game instance 1074 includes or is provided based on the game dataupdates 1078. As a result, the game images/output 1084 provided by theplatform output devices 1080 is “live” or provides real time feedbackafter the authoring messages 1050 and/or 1052 are transmitted.

Significantly, the messages 1050, 1052 may be transmitted independentlyor in an overlapping manner to support collaborative authoring as a userof development system 1010 or 1030 may continue work with tool 1020 and1040 to author or modify the game 1074. In other words, “concurrent”and/or collaborative authoring is generally intended to mean that two ormore tools 1020, 1040 may work on a single game instance 1074 (orinstances running on two or more platforms 1070) and communicate changesor updates with each other and/or with the running game (e.g., to havereal time or live feedback regarding the changes provided by operationof the game platform 1070 and in their tool GUIs 1014, 1034). Theupdates 1029, 1048 made by one or both of the tools 1020, 1040 are alsoreflected in the tool's game data 1028, 1046 such that work by eachdeveloper is provided in a timely manner to each developer, and the toolGUI 1014, 1034 may include the updates 1029, 1048 such as shown withcollaborating author changes 1015, 1035 (e.g., changes made by the otherone of the authors and not just with the tool 1020 or 1040 associateddirectly with the tool GUI 1014, 1034).

FIGS. 11A and 11B illustrate screenshots 1120, 1140 that may be providedduring operation of the system 1000 of FIG. 10. As shown in FIG. 11A, agame platform 1070 may be running an instance of a game 1074 and with afirst set of game data 1076 may create the output 1084 shown inscreenshot 1120 on the platform monitor 1080. In the screenshot 1120, acharacter 1122 is shown jumping from scene element/object 1128 (e.g., afloor, the ground, or the like) toward or onto another game object 1126(e.g., a platform, a column, or the like). As shown, the column or gameobject 1126 has a particular position in the game level or scene, andthe floor or game object 1128 has a texture 1130 (which is shown to beat a first stage of development/completion).

As shown in FIG. 11B, the game platform 1070 may continue to run theinstance of the game 1074 but with a set of game data 1076 that has beenupdated with game data changes/modifications 1078. In this example, theupdates 1078 have been provided by two tools 1020, 1040 with one toolbeing used for texturing the floor 1128 while the other is being used toadjust object positions. Hence, as shown in FIG. 11B, the screenshot1140 shows the floor 1128 at a later stage of development/completion forthe texture 1131 (or, in some cases, the texture/material 1131 may be anewly created and applied texture/material). Also, the screenshot 1140shows the column or game object 1126 being moved as shown with arrow1127 to a new position relative to the character 1122 (e.g., to make ajump or other move easier or harder). Numerous other changes may be madeby allowing two or more tools 1020, 1040 to access a live instance of agame 1074 and to provide updates 1078 to the game data 1076. Also, thechanges 1078 (such as the modification of the texture 1130 to 1131) maybe transmitted to the other tool 1020, 1040 and reflected (whenappropriate) in the tool GUI 1014, 1034 such as when the tool interfaceincludes a representation of a game object whose texture or othercharacteristics have changed as result of game updates performed byanother tool.

The hub communications applications and tool-to-game platformcommunication techniques described herein may also be utilized toprovide unique and effective playtesting of video games. The playtestingdescribed below may be thought of as “real-time” in that collected datafrom the game is transmitted via the communications hub to a playtestingmonitoring system (or developers workstation/computer) and presented asthe playtesting is occurring (e.g., with no or minor delays) on one ormore monitors. Real-time playtesting turns what used to be a static gametesting environment into a dynamic, interactive process. Interactivityis provided by the use of development tools or other devices to transmitgame modifications (e.g., changing logic to make a function or processeasier or harder or the like) via the communications hub to the gameplatforms (which may be differing types of platforms requiring differingcommunication protocols for messaging) where the game engine running thevideo game application uses the modified game data to nearlyinstantaneous provide a revised game to the game players (e.g., all ofthe games may be modified in a like manner or a subset may be modifiedto determine if the change has a desired or predicted effect).

In some preferred embodiments, the video game testing system is adaptedsuch that the game play data is monitored in real time rather thanevaluating the results of a given testing session after the fact (e.g.,days or weeks after the test group has left the test facility). Data iscollected from each game player or individual tester and reported backto a centralized location such as a monitoring computer system or adeveloper's workstation adapted for playtest monitoring. From thiscentral location or system, changes can be made by the developer such asby operating a video game development tool to transmit authoringmessages with new game data/content to via the communications hubapplication to one or more of the running video games (e.g., a game modrecipient set). The results of this game modification or change can bedetermined nearly immediately because the game players or individualtesters are still in the test facility and play the revised running gameor instance of the game on one or more game platforms. For example, if asignificant portion such as a majority of the game players are havingdifficulty completing a given jump (or other game task/function), thelevel designers or other development team members can “on the fly” or innear real time shorten the distance to see if this modification to therunning game helps increase the success rate to a desired level (e.g.,still some amount miss the jump if desirable to provide a challenge atthis point in the game). A statistics gathering tool may be run to storethe change to game data and when in the test that the change was madesuch that the game modification or “tweak” is tracked and stored alongwith other playtest tracking data.

The game modification may be made on all game platforms or in allrunning game instances or for some smaller fraction or subset (e.g., 50percent, 10 percent, 80 percent or the like), and the players may begrouped based on one or more criteria and the subset selected out of oneor more of these groups (e.g., modify 30 percent of the running gamesfor the highest skill level players, modify 70 percent of the runninggames for the players under 30 years old, modify 40 percent of therunning games for the male players, or nearly any other combination offraction of the games and grouping of players). The use of real-timemonitoring of playtesting combined with modifying the game in a singleplay session ensures that the playtesters or test group of players is ofa consistent skill level, which in the past had led to wide ranges ofresults as the skill of two groups of players often varied widely. Thecommunications hub application allows any number of game clients toconnect and send nearly any type of game play information or datathrough the hub to a statistics gathering and processing tool(s) forreal-time processing/evaluation and display to monitoring individuals(e.g., members of the development team). One or more authoring or gamedevelopment tools can connect to the same communications hub applicationand distribute tweaks or modifications to the game data to some or allof the playtesters during the playtest.

FIG. 12 illustrates a video game playtesting system 1200 of anembodiment of the invention that is adapted for providing developerswith real-time feedback of test results and also for allowing thesedevelopers to make changes to the running video games while the samecontrol group is available to play the game. As shown, the system 1200includes a playtesting facility 1210 in which a plurality of gameplatforms 1212 are provided, and, as discussed above, these may be thesame platform or may vary to allow the same game to be tested on avariety of consoles/systems. Each platform 1212 includes a game engine1214 to run a video game application 1216 (or a portion that is readyfor testing) based on a set of game data 1218, which typically will bein an initial testing state and then will include test modifications orchanges 1220 as discussed below to tweak or change some game feature(such as amount of life or energy lost at being struck by an opponent orthe like) after gathering and processing a quantity (e.g., a half hour,an hour, a number of attempts or repeats of a level or game portion, orthe like) of test or play data. A display and/or output device 1224 isprovided as part of the platform 1212 and operates during game play ortesting to provide game images and other output such as audio andtactile feedback output.

As the game 1216 is played by a set of testers, game play data 1230 istransmitted to the hub server 350 that includes a communications hubapplication 354 that communicates (as discussed in detail above) usingclient communications libraries 360 and client lists 358 stored inmemory with the game platforms 1212 and with a playtest monitoringsystem 1240. In particular, the hub application 354 forwards the gameplay data 1230 to the playtest monitoring system 1240 in a formaccepted/expected by the monitoring system 1240 (or client applicationsrunning thereon such as the statistics gathering tool 1250 and gamedevelopment tool(s) 1254) as testing data messages 1232.

The monitoring system 1240 often will be operated by a game developer ordevelopment team member to tweak or fine tune aspects of a video game1216 during or as part of performing playtesting at the facility 1210.To this end, the system 1240 includes I/O devices 1243 managed by a CPU1242 to allow an operator to input or select game changes or testmodifications 1264 via interaction with a game development tool 1254and/or to view and manipulate results of game testing. A monitor 1244 isprovided that may be used by a playtesting statistics gathering tool1250 to display a test monitoring interface 1246, e.g., to displayaggregated playtest information to the developer. The monitor 1244 mayalso be used by the game development tool 1254 to display a developmenttool GUI 1245 to display the game data 1262 that is presently being usedby the game (shown at 1218) and is being tested and to allow thedeveloper to make changes or tweaks to the game logic or other gameassets/settings (e.g., shorten a jump, increase life/energy of acharacter upon reaching a check point, and so on). In other embodiments,a separate tool is utilized that is not necessarily part of the monitor1244.

As discussed above, the development tool 1254 may use a built in (oraccessible) hub communications library 1256 to communicate with the hubapplication 354 with game authoring messages 1270 that typically willinclude testing mods or game data changes 1264 made via the tool 1254and interface 1245. The hub application 354 determines the appropriateclients and sends test modification messages 1276 to the clients or gameapplications 1216 on various platforms 1212 in the facility 1212 (or toother development tools as discussed above). The clients receiving themodification messages 1276 may then modify their game data 1218 toinclude the modifications 1220 and the running video game 1216 willreflect the changes to allow the testing by the same control group tocontinue to verify the effectiveness or usefulness of the changes. Thegames 1216 receiving the changes 1220 may be all of the running games1216 or some smaller subset selected by an operator of the monitoringsystem 1240 such as a fraction of all games or a fraction of a subgroupof the games and so on.

The playtesting statistics gathering tool 1250 may function to recordall the received data 1266 in memory 1260, but, typically, the tool 1250also is configured to perform aggregation functions and to presentprocessed/aggregated data 1247 within an interface 1246. For example,the gathering tool 1250 may act to generate and store 1266 and thendisplay aggregated statistics 1247 such as numbers of players, averagescoring/energy at various game checkpoints, number of players heating alevel or challenge and how many attempts it requires, and so on. Thisaggregation of statistics by tool 1250 is preferably done on an ongoingbasis concurrently with the operation of the playtesting facility 1210such that developers have real-time feedback on the results of theplaytesting of the game 1216. The statistics gathering tool 1250 mayalso display player statistics for each of the players as shown at 1248in interface 1246. The individual player stats 1248 may includedemographic information such as age and sex as well as other more gamingspecific information such as number of years of gaming experience andskill ranking (if available, while the system 1200 is useful in someaspects not because of knowledge of the skill levels but because thecontrol group is the same before and after a test mod 1220 is sent toand implemented in a running game 1216).

FIGS. 13 and 14 illustrate a pair of screen shots 1310 and 1410 that maybe provided by the statistics gathering tool of the system 1200. In thescreenshot 1310, the monitor screen is divided into two areas with onedisplaying player statistics in player windows/boxes 1320 and the otherportion 1350 being used to display aggregated playtest statistics. Forexample, a player window 1320 may be provided for each member of thecontrol group or each tester. In this embodiment, a thumbnail of thegame playing status or game screen shot 1322 is provided that showswhere the player is in the game (e.g., with a still shot that isperiodically updated or the like), but the game position/status may beprovided also with text, symbols, and other displayed information. Theplayer window 1320 also includes a player data section 1330 thatprovides the developer or playtest monitor with information about thegame player or tester. For example, but not as a limitation, the playerdata 1330 may include a player ID 1332 for each player along with agame/client address 1336 such as would allow the test monitor totransmit test mod messages to specific ones of the testers to test agame change. The player data 1330 may also include demographicinformation 1334 such as age, sex, and the like and, if theplayers/testers are grouped as part of the testing (or by the statisticsgathering tool), the demographics or player ID may include informationindicating which group or subset of the game testers or control groupthe player has been assigned. Game status information 1340 may also beprovided in the player data 1330 such as their current score 1342, theamount of life or energy 1344 their character has in the game, and otherstatistics such as position in the game.

The testing described herein preferably includes some level ofprocessing or aggregating of the game data from the testers tofacilitate game development and decisions on how to improve the currentgame version. To this end, the aggregation section 1350 includes a title1352 indicating which game is described and includes a number ofaggregated statistics or game test results determined by processingand/or aggregating the collected test data. For example, the statistics1350 may include average scoring for a game or portion of game 1354, mayinclude percentage of players that lose or die at particular locationsor tasks of the game 1356, may include average damage or loss ofenergy/life at various points of games 1358 (e.g., how much energy doesit require to reach a checkpoint or to perform a battle, and so on),and/or may include number of players passing/beating a level on a first(or other) attempt. Numerous other statistics or playtest results may bedetermined by the statistics gathering tool and displayed in aninterface as shown with screenshot 1310. In some cases, the system isalso used to capture spatial information that can be overlaid on top ofan authoring environment to provide context (e.g., where do people dieor fail often in a game or the like).

In alternate or additional screenshot 1410, the statistics gatheringtool may be used to group the game players or testers into groups basedon various criteria and to display these various groups (or the playerwindows 1320 and their aggregated statistics 1350). For example, thecriteria used to form three groups 1420, 1430, 1440 may be age or skilllevels or these variable combined with gender of the players such aswhen the game may be more targeted to particular ages (such as tweens)or to particular genders. As shown, within each grouping on the screen1410, a set of player windows 1424, 1434, 1444 are provided to allow atest monitor to quickly determine the status of the various players ortesters in each group. Though not shown, a statistics/aggregated resultswindow/box such as shown at 1350 may be provided for each group 1420,1430, 1440 to allow the test monitor to more rapidly compare the playingexperience for each group (e.g., one group finds the game or a portionof the game easy or hard while another group may have a very differentexperience). The output or game test data displayed in the screenshots1310, 1410 may be utilized by a game developer to select test or gamemodifications (via operation of a game development tool) to implementwithin the entire control group or just on the machines/platforms ofparticular groups, fractions of groups, or even individual players.

FIG. 15 illustrates a playtesting method 1500 that may be implemented byoperation of the system 1200. The method 1500 starts at 1505 such aswith selection of a video game for playtesting, establishing a testingprotocol, identification of a control group or set of testers, andgathering demographic data on the testers. At 1510, the method 1500includes configuring the testing system for hub communications such asby installing/loading a central hub application and communicativelylinking this hub application with the game platforms in a test facilityand game development tools to allow real-time game modifications duringa test. At 1520, the method 1500 includes linking or connecting one ormore statistics gathering tools to the hub application, and thestatistics gathering tool may run on any computer device within the testsystem such as on the hub server or a developer workstation. At 1530,the method 1500 includes identifying a test group and storing playerdata in memory accessible by the statistics gathering tool.

At 1536, the method 1500 includes initiating game play in a testfacility (or in platforms in a distributed test system which may eveninclude online game testing as “facility” is not intended to be limitingto a particular physical location or room). In step 1536, a video gameis run on a plurality of game platforms that may be the sameconfiguration (e.g., all from one platform company) or may vary as thecommunications hub application allows the statistics gathering tool (anddevelopment tools) to communicate including receiving game play datafrom the various platforms and sending game data changes or authoringmessages from the development tool to the running games. At 1540, themethod 1500 includes collecting game play data as the games are playedby the control group of testers or game players and also using thestatistics gathering tool to store this data, to aggregate and/orprocess the data, and to determine various statistics or test parametersor values based on the game data.

At 1550, the statistics gathering tool provides a test monitoringinterface on a monitor of a developer workstation or monitoring system,and the interface includes at least portions of the gathered game datasuch as calculated statistics and/or player data and status information(e.g., see FIGS. 13 and 14). At 1560, the developer may act to make gamechanges or modifications based on the displayed game data/statistics,e.g., operate a game development tool to change game logic, to changegame assets, and/or so on. The method 1500 includes determining whetherthe modifications are made either automatically as discussed with anauthoring tool or in response to an authoring message being sent by thedevelopment tool (e.g., manual message creation and transmission). At1570, when a modification is made, the method 1500 continues with usingthe communications hub application to identify clients (e.g., gamesrunning on platforms in a test facility based on content and/or basedupon addressees in the messages such as a subset of the games in thecontrol group). The messages are transmitted in proper format for thevarious platforms. At 1580, the game engines are used to run video gameswith test modifications on all or a subset of the game platforms. Themethod 1500 may continue at 1540 to repeat gathering data after the gameplay data has been changed and tested by the control group. Additionalchanges may be made at 1560 in an iterative process (e.g., real-timegame testing and updating/development). At 1590, the method 1500 endssuch as at the end of the playtest session.

Although the invention has been described and illustrated with a certaindegree of particularity, it is understood that the present disclosurehas been made only by way of example, and that numerous changes in thecombination and arrangement of parts can be resorted to by those skilledin the art without departing from the spirit and scope of the invention,as hereinafter claimed. For example, the playtesting methods describedherein may be used with testing and developing other forms of softwareand other products in which feedback may be provided by computersoftware through a communications hub application to a monitoringsystem. In such product development environments, the testinginformation is gathered, processed, and displayed at least with someoverlap with the testing session (e.g., while the testers are stillavailable to test product modifications). A software development orauthoring tool is used to transmit product modifications to the testingfacilities (e.g., a set of computers or electronic devices running asoftware application) such as by sending authoring messages with contentincluding such changes via the communication hub module or application.The modified product is tested with the implemented modifications by thesame or nearly the same control group, and the results/data are sent tothe statistics gathering tool for processing and/or display on themonitoring station. This iterative, real-time process is effective formore quickly fixing usability issues with software products and also forfine tuning product features and design aspects in response to testerfeedback or tester experiences (as measured by collection of test data).

1. A communication method provided in a communication hub application ona computer linked to a communications network for a video gamedevelopment system, comprising: receiving a message including game datafrom a video game development tool running on a developer workstation;identifying at least one message recipient for the received message inthe video game development system, the at least one message recipientbeing one of a plurality of differing video game platforms, each videogame platform providing a different communication library definingmessaging or other communications for such platform; reformatting thereceived message based on the communications library corresponding toeach of the identified message recipients to form at least onerecipient-specific message, wherein each of the recipient-specificmessages is in a configuration associated with the communicationslibrary of the corresponding identified message recipient; andtransmitting each of the recipient-specific messages to each of theidentified message recipients.
 2. The method of claim 1, wherein themessage received from the game development tool has a configurationdefined by a set of hub application communications data, wherein theconfiguration of the received message differs from at least one of theconfigurations of the recipient-specific messages, and wherein the setof hub application communications data is stored in memory on thedeveloper workstation for access by the game development tool.
 3. Themethod of claim 1, wherein the identifying of the message recipientscomprises registering a set of clients including instances of a videogame running on a set of video game platforms, the method furthercomprising determining from game data content in the received message asubset of the registered clients to identify as the message recipients,and wherein the set of clients includes subsystems of the video gameinstances affected by modifications to game data in the game datacontent in the received message.
 4. The method of claim 1, furthercomprising receiving a second message from a second game developmenttool running in the video game development system, wherein the messagesreceived from the game development tool and the second game developmenttool have a single configuration defined by a set of hub applicationcommunications data.
 5. The method of claim 4, wherein theconfigurations of the received messages differ from at least one of theconfigurations of the recipient-specific messages and wherein the secondreceived message comprises a list of addressees including the gamedevelopment tool running on the developer workstation.
 6. A video gamedevelopment system facilitating communications with at least first andsecond video game platforms based on at least first and secondcommunication libraries, respectively, comprising: a communications hubmodule running on a hub server communicatively linked with the first andsecond video game platforms; memory accessible by the communications hubmodule storing the first and second communication libraries; and a videogame development tool running on a computer system and communicativelylinked with the communications hub module, the video game developmenttool transmitting messages configured based on a client-sidecommunications library providing communication protocols for thecommunications hub module, wherein the communications hub modulereceives the transmitted messages, generates first and second gameplatform messages from the received messages based on the first andsecond communication libraries, respectively, and forwards the gameplatform messages to the first and second video game platforms andwherein the first game platform messages have a differing format thanthe second game platform messages.
 7. The system of claim 6, wherein themessages transmitted by the video game development tool include gamedata for a video game running on the first and second video gameplatforms and wherein the game platform messages are forwarded to boththe first and the second video game platforms.
 8. The system of claim 7,wherein the communications hub module processes each of the messagestransmitted by the video game development tool to determine a list ofrecipients for each of the game platform messages.
 9. The system ofclaim 8, wherein the list of recipients is determined based on a set ofaddressees provided in the messages transmitted by the video gamedevelopment tool.
 10. The system of claim 9, wherein the video gamedevelopment system further includes a second video game development toollinked with the communications hub module and wherein the second videogame development tool is specified in the set of addressees or is placedon the list of recipients based on the game data in the transmittedmessages.
 11. The system of claim 8, wherein the list of recipients isdetermined from a list of clients registered with the communications hubmodule to receive messages from video game development tools and whereinthe registered clients include subsystems of games running upon thefirst and second video game platforms.
 12. The system of claim 6,wherein the video game development tool uses a single communicationssocket to send the transmitted messages to both the first and secondvideo game platforms via the communications hub module.
 13. The systemof claim 12, wherein the communications hub module provides acommunication interface between the video game development tool and thefirst and second video game platforms including maintainingcommunication sockets to the first and second video game platforms andimplementing protocols in the first and second communication libraries.14. A communication method for a video game development system,comprising: providing a communication hub application on a computerlinked to a communications network; with the communication huhapplication, receiving a message from a game development tool running ona developer workstation; identifying message recipients for the receivedmessage in the video game development system; processing the receivedmessage based on communications libraries corresponding to each of theidentified message recipients to form a set of recipient specificmessages, whereby the recipient-specific messages are in two or moreconfigurations associated with corresponding ones of the identifiedmessage recipients; and transmitting the recipient-specific messagesfrom the computer running the communication hub application to theidentified message recipients.
 15. The method of claim 14, wherein themessage received from the game development tool has a configurationdefined by a set of hub application communications data and wherein theconfiguration of the received message differs from at least one of theconfigurations of the recipient-specific messages.
 16. The method ofclaim 14, wherein the set of hub application communications data isstored in memory on the developer workstation for access by the gamedevelopment tool.
 17. The method of claim 14, wherein the identifying ofthe message recipients comprises registering a set of clients includinginstances of a video game running on a set of video game platforms andfurther comprises determining from game data content in the receivedmessage a subset of the registered clients to identify as the messagerecipients.
 18. The method of claim 17, wherein the set of clientsincludes subsystems of the video game instances affected bymodifications to game data in the game data content in the receivedmessage.
 19. The method of claim 14, further comprising receiving asecond message from a second game development tool running in the videogame development system, wherein the messages received from the gamedevelopment tool and the second game development tool have a singleconfiguration defined by a set of hub application communications dataand wherein the configurations of the received messages differ from atleast one of the configurations of the recipient-specific messages. 20.The method of claim 19, wherein the second received message comprises alist of addressees including the game development tool running on thedeveloper workstation.